-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move CheckLimitsForResolvConf to Kubelet#syncLoop #84253
Conversation
/test pull-kubernetes-node-e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Makes sense to me to only do this once :)
f71d2ee
to
ae9e93d
Compare
@mattjmcnaughton |
/test pull-kubernetes-e2e-gce-100-performance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Still looks good to me :)
/assign @MrHohn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks and sorry for the delay.
/lgtm
/approve
/priority important-soon |
Is this check just informational, for debugging purposes? |
@tallclair |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrHohn, tallclair, tedyu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kubernetes-integration |
I am not sure this really improved anything. If network manager is restarted or the kubelet has a race with network manager, its possible the contents of /etc/resolv.conf could change underneath us. I preferred checking the contents of the file in the iteration loop rather than checking it once for the life of the process. It makes changes are harder to debug if/when there are actual problems. |
I am fine with checking /etc/resolv.conf more than once.
where
|
Currently the check logs a warning. |
@tedyu that makes sense. |
Here is skeleton of proposed change for CheckLimitsForResolvConf (showing only one of the 4 klog's):
@derekwaynecarr |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR moves the CheckLimitsForResolvConf to Kubelet#syncLoop.
Which issue(s) this PR fixes:
Fixes #80070
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: